Multi-purposed self-propelled device

ABSTRACT

Disclosed are a multi-purposed, self-propelled device and method for operation of the self-propelled device. Certain variations can include a spherical housing having an internal drive system and a multifunctional payload space for use in a variety of applications.

RELATED APPLICATION

This application claims priority to U.S. Provisional Patent Application Ser. No. 61/820,109, entitled, “MULTI-PURPOSED SELF-PROPELLED DEVICE,” filed May 6, 2013; the aforementioned application being hereby incorporated by reference in its entirety.

This application is a Continuation-in-Part of U.S. patent application Ser. No. 14/035,841, entitled “SELF-PROPELLED DEVICE WITH ACTIVELY ENGAGED DRIVE SYSTEM”, filed Sep. 24, 2013; which is a Continuation of Ser. No. 13/342,853, entitled “SELF-PROPELLED DEVICE WITH ACTIVELY ENGAGED DRIVE SYSTEM”, filed Jan. 3, 2012, now U.S. Pat. No. 8,571,781, issued Oct. 29, 2013; which claims benefit of priority to the following: U.S. Provisional Application No. 61/430,023, entitled “METHOD AND SYSTEM FOR CONTROLLING A ROBOTIC DEVICE, filed Jan. 5, 2011; U.S. Provisional Application No. 61/430,083, entitled “SYSTEM AND METHOD FOR ESTABLISHING 2-WAY COMMUNICATION FOR CONTROLLING A ROBOTIC DEVICE”, filed Jan. 5, 2011 and U.S. Provisional Application No. 61/553,923, entitled “A SELF-PROPELLED DEVICE AND SYSTEM FOR CONTROLLING SAME”, filed Oct. 31, 2011; all of the aforementioned priority applications being hereby incorporated by reference in their respective entirety for all purposes.

TECHNICAL FIELD

Examples described herein relate to a multi-purpose remotely controllable self-propelled device.

BACKGROUND

Various types of remotely controllable devices exist. For example hobbyists often operate remote controlled devices in the form of cars, trucks, airplanes and helicopters. Such devices typically receive commands from a controller device, and after movement (e.g., direction or velocity) based on the input. Some devices use software-based controllers, which can be implemented in the form of an application running on a device such as a smart phone or a tablet.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure herein is illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings in which like reference numerals refer to similar elements, and in which:

FIG. 1 is an example block diagram illustrating the components of a self-propelled device that is in the form of a spherical ball;

FIG. 2A is an example block diagram illustrating a self-propelled device;

FIG. 2B is an example block diagram illustrating a self-propelled device with an alternative biasing mechanism;

FIG. 2C is an example block diagram illustrating a self-propelled device with another alternative biasing mechanism to improve payload space;

FIG. 3 is an example block diagram illustrating a self-propelled device including an attached camera therein;

FIG. 4 is an example block diagram illustrating a self-propelled device including a payload;

FIG. 5 is an example schematic depiction of a self-propelled device and a controller device;

FIG. 6 illustrates an example technique for causing motion of a self-propelled spherical device;

FIG. 7 is an example block diagram depicting a sensor array and data flow;

FIG. 8 illustrates an example system including a self-propelled device and a controller device to control and interact with the self-propelled device; and

FIG. 9 is an example flow chart illustrating a method of operating a self-propelled device.

DETAILED DESCRIPTION

A multi-purposed self-propelled device is provided which includes a drive system, a spherical housing, a biasing mechanism, and a payload space within the spherical housing. The biasing mechanism can include single extended spring to engage an inner surface of the spherical housing diametrically opposed to a contact surface engaged by the drive system. Alternatively, the biasing mechanism can include one or more (e.g., a pair) of portal axles each having a spring and contact element to push against a respective contact point in the inner surface of the spherical housing. As such, the portal axles can produce a vertical force that similarly actively forces the drive system to continuously engage the inner surface of the spherical housing in order to cause the spherical housing to move. The self-propelled device can be implemented to carry a payload or multiple payloads for various uses and activities.

The payload space can be utilized to carry any payload. For example, the payload can include a camera, which can send images and/or a video stream from the self-propelled device to a controller device. The controller device can be in the form of a smartphone, tablet, or any other suitable operating device. Further, the spherical housing can be transparent to allow the camera to take images or real time video, thereby allowing a user of the controller device (e.g. smartphone) to control the self-propelled device by viewing the video stream.

In still other variations, the payload space includes a single payload or multiple payloads for civilian or military use. Such payloads can include one or more of: a camera, an infrared sensor, a chemical sensor, a biological sensor, one or more explosives, a listening device, or any other payload that can fit within the payload space.

For variations including a camera or other image capturing device, a touch a drive method is disclosed that provides the user with the ability to dynamically control the self-propelled device by touching location points on a live image or video feed. The method includes receiving an image or live video feed from the self-propelled device that provides a field of view of the camera mounted within the self-propelled device. This video feed can be displayed on a touch-sensitive display of the controlled or mobile computing device. The method further includes receiving, on the touch-sensitive display, a user selection of a location point within the field of view of the camera, and based on the user selection, generating a command signal to be transmitted to the self-propelled device instructing the self-propelled device to maneuver to the location point.

Furthermore, the method can include determining a position of the location point in the field of view based on a first reference frame of the field of view as displayed on the controller device, and mapping the position of the location point on a second reference frame corresponding to the location point relative to the self-propelled device. In such arrangements, the command signal is generated to include instructions for maneuvering the self-propelled device based solely on the second reference frame. Further still, for live video feed implementations, the controller device can generate the command signal dynamically in conjunction with receiving the live video feed.

System Overview

Referring to the drawings, FIG. 1 is an example block diagram illustrating the components of a self-propelled device that is in the form of a spherical ball. A multi-purposed self-propelled device 100 can be operated to move under control of another device, such as a computing device (e.g. a smartphone, tablet, and/or remote control) operated by a user. The self-propelled device 100 can be configured with resources that enable one or more of the following: (i) maintain self-awareness of orientation and/or position relative to an initial reference frame after the device initiates movement; (ii) process control input programmatically, so as to enable a diverse range of program-specific responses to different control inputs; (iii) enable another device to control its movement using software or programming logic that is communicative with programming logic on the self-propelled device; and/or (iv) generate an output response for its movement and state that it is software interpretable by the control device.

For example, the multi-purposed self-propelled device 100 can include several interconnected subsystems and modules. A processor 114 executes programmatic instructions from a program memory 104. The instructions stored in the program memory 104 can be changed, for example to add features, correct flaws, or modify behavior. In some examples, the program memory 104 stores programming instructions that are communicative or otherwise operable with software executing on a computing device. The processor 114 can be configured to execute different programs of programming instructions, in order to after the manner in which the self-propelled device 100 interprets or otherwise responds to control input from another computing device.

A wireless communication module 110, in conjunction with a communication transducer 102, can serve to exchange data between processor 114 and other external devices. The data exchanges, for example, can provide communications, provide control, provide logical instructions, state information, and/or provide updates for the program memory 104. In some examples, the processor 114 can generate output corresponding to state and/or position information, that can then be communicated to the controller device via a wireless communication port. The mobility of the device makes wired connections undesirable. Therefore, the term “connection” can be understood to describe a logical link made without a physical attachment to the self-propelled device 100.

In some examples, the wireless communication module 110 can implement a BLUETOOTH communications protocol and the transducer 102 can be an antenna suitable for transmission and reception of BLUETOOTH signals. As an addition or alternative, the wireless communication module 110 can implement a Wi-Fi communications protocol and the transducer can be an antenna suitable for transmission and reception of Wi-Fi signals. In such examples, the self-propelled device 100 can be controlled by a controller device via BLUETOOTH and/or Wi-Fi signals. Other wireless communication mediums and protocols can also be used in alternative implementations.

Sensors 112 can provide information about the surrounding environment and condition to the processor 114. In variations, the sensors 112 include inertial measurement devices, including a three-axis gyroscope, a three-axis accelerometer, and a three-axis magnetometer. Furthermore, the sensors 112 can provide input to enable the processor 114 to maintain awareness of the device's orientation and/or position relative to the initial reference frame after the device initiates movement. The sensors 112 can include instruments for detecting light, temperature, humidity, or measuring chemical concentrations or radioactivity.

State/variable memory 106 can store information about the state of the device, including, for example, position, orientation, rates of rotation and translation in each axis. The state/variable memory 106 can also store information corresponding to an initial reference frame of the device upon, for example, the device being put in use (e.g., the device being activated), as well as position and orientation information once the device is in use. In this manner, the self-propelled device 100 can utilize information of the state/variable memory 106 in order to maintain position and orientation information of the self-propelled device 100 once the device is in operation.

A clock 108 can provide timing information to the processor 114. For example, the clock 108 can provide a time base for measuring intervals and rates of change. Furthermore, the clock 108 can provide day, date, year, time, and alarm functions. Further still, the clock 108 can allow the self-propelled device 100 to provide an alarm or alert at pre-set times.

An expansion port 120 can provide a connection for addition of accessories or devices. Expansion port 120 provides for future expansion, as well as flexibility to add options or enhancements. For example, expansion port 120 can be used to add peripherals, sensors, processing hardware, storage, displays, or actuators to the self-propelled device 100.

As an addition or alternative, the expansion port 120 can provide an interface capable of communicating with a suitably configured component using analog or digital signals. The expansion port 120 can provide electrical interfaces and protocols that are standard or well-known. The expansion port 120 can further implement an optical interface. For example, interfaces appropriate for expansion port 120 include a Universal Serial Bus (USB), Inter-Integrated Circuit Bus (I2C), Serial Peripheral Interface (SPI), or ETHERNET.

A display 118 presents information to outside devices or persons. The display 118 can present information in a variety of forms. In various examples, the display 118 can produce light in colors and patterns, sound, vibration, or combinations of sensory stimuli. In some examples, the display 118 can operate in conjunction with actuators 126 to communicate information by physical movements of the self-propelled device 100. For example, the self-propelled device 100 can be made to emulate a human head nod or shake to communicate “yes” or “no.”

As an addition or alternative, the display 118 can be configured to emit light, either in the visible or invisible range. Invisible light in the infrared or ultraviolet range can be useful, for example, to send information invisible to human senses but available to specialized detectors. Furthermore, the display 118 can include an array of Light Emitting Diodes (LEDs) emitting various light frequencies, arranged such that their relative intensity can be variable and the light emitted can be blended to form color mixtures.

As an addition or alternative, the display 118 includes an LED array comprising several LEDs, each emitting a human-visible primary color. The processor 114 can vary the relative intensity of each LED to produce a wide range of colors. Primary colors of light are those wherein a few colors can be blended in different amounts to produce a wide gamut of apparent colors. Many sets of primary colors of light are known, including for example red/green/blue, red/green/blue/white, and red/green/blue/amber. For example, red, green, and blue LEDs together comprise a usable set of three available primary-color devices comprising the display 118. In variations, other sets of primary colors and white LEDs can be used. In many implementations, the display 118 can include one or more LEDs used to indicate a reference point on the self-propelled device 100 for alignment.

An energy storage unit 124 stores energy for operating the electronics and electromechanical components of the self-propelled device 100. For example, the energy storage unit 124 can be a rechargeable battery. An inductive charge port 128 can allow for recharging the energy storage unit 124 without a wired electrical connection. Furthermore, inductive charge port 128 can receive magnetic energy and convert it to electrical energy to recharge the energy storage unit 124. As an addition or alternative, the inductive charge port 128 can provide a wireless communication interface with an external charging device. Further, a plug in charging means can be included as an addition or alternative to the inductive charge port 128.

A deep sleep sensor 122 can be included to place the self-propelled device 100 into a very low power or “deep sleep” mode where most of the electronic devices use no power. This may useful for long-term storage, shipping, and/or certain implementations of the self-propelled device 100 that require such a state. For example, the self-propelled device 100 can be implemented to carry a payload, such as a camera, a motion sensor, an infrared sensor and/or a chemical or biological sensor. In such variations, the self-propelled device 100 can sit dormant in the deep sleep mode until a trigger, such as an event setting off the camera or one or more sensors, automatically activates the self-propelled device 100.

In variations, the sensors 122 can sense objects, events, incidents, matter, and/or phenomena through the spherical housing of self-propelled device 100 without a wired connection. As an addition or alternative, the deep sleep sensor 122 may be a Hall Effect sensor mounted in a manner such that an external magnet can be applied on the self-propelled device 100 to activate the deep sleep mode.

The drive system actuators 126 can convert electrical energy into mechanical energy for various uses. A primary use of the actuators 126 can be to propel and steer the self-propelled device 100. Movement and steering actuators can also be referred to as a drive system or traction system. The drive system causes rotational and translational movement of the self-propelled device 100 under control of the processor 114. Examples of the actuators 126 can include, for example, wheels, motors, solenoids, propellers, paddle wheels, and pendulums.

For example, the drive system actuators 126 can include a set of two parallel wheels, each mounted to an axle connected to independently variable-speed motors through a reduction gear system. In such examples, the operation of the two independently operated drive motors can be controlled by processor 114.

However, the actuators 126 may produce a variety of movements in addition to rotating and translating self-propelled device 100. For example, the actuators 126 can cause self-propelled device 100 to execute communicative movements, including emulation of human gestures, for example, head nodding, shaking, trembling, spinning or flipping. In variations, the processor coordinates the actuators 126 with the display 118. Similarly, the processor 114 can provide signals to the actuators 126 and the display 118 to cause the self-propelled device 100 to spin or tremble and simultaneously emit patterns of colored light. As an addition or alternative, the self-propelled device 100 can emit light or sound patterns synchronized with movements.

The self-propelled device 100 can be used as a controller for other network-connected devices. The self-propelled device 100 can contain sensors and wireless communication capabilities, so that it may perform a controller role for other devices. For example, the self-propelled device 100 may be held in the hand and used to sense gestures, movements, rotations, combination inputs and the like.

Mechanical Design

FIG. 2A is an example block diagram illustrating a self-propelled device. The self-propelled device 200 can be multi-purposed and can include a spherical housing 202, a drive system 201, a biasing mechanism 215, and a payload space 228. For example, the self-propelled device 200 may be in the form of a robotic, spherical ball. The self-propelled device 200 can be of a size and weight allowing it to be easily grasped, lifted, and carried in an adult human hand. In variations, the self-propelled device 200 may be larger or smaller, and/or customized for a particular payload. For example, the self-propelled device 200 may be manufactured to include a transparent spherical housing, and a camera may be included within the payload space to provide a video stream to the controller device, such as for example as smartphone or tablet, as shown by an example of FIG. 3.

Referring still to FIG. 2A, the self-propelled device 200 includes an outer spherical shell (or housing) 202 that makes contact with an external surface as the device rolls. In addition, the self-propelled device 200 includes an inner surface 204 of the spherical housing 202, wherein wheels 218 and 220 included as components of the drive system 201 make contact with the inner surface 204 to cause the self-propelled device 200 to move. Additionally, the self-propelled device 200 can include several mechanical and electronic components enclosed within the spherical housing 202.

The spherical housing 202 can be at least partially composed of one or more materials that allow for the transmission of signals used for wireless communication, and yet can be impervious to moisture and dirt. The spherical housing 202 material can be durable, washable, and/or shatter resistant. The spherical housing 202 can also be structured to enable transmission of light and can be textured to diffuse the light.

In variations, the spherical housing 202 can be made of a sealed polycarbonate plastic. In similar variations, at least one of the spherical housing 202, or the inner surface 204, can be textured to diffuse light. As an addition or an alternative, the spherical housing 202 can comprise two hemispherical shells with an associated attachment mechanism, such that the spherical housing 202 can be opened to allow access to the internal electronic and mechanical components. In similar variations, the spherical housing 202 can include automatic opening means configured to open the housing upon a command prompt by a user using the controller device. As an addition or alternative, the spherical housing 202 can be opened to deposit a payload placed in a payload space 228, and then subsequently closed such that the user can continue maneuvering the self-propelled device 200. The spherical housing 202 can further include a treaded outer surface, or an outer surface that includes knobs and/or nodules for traction.

Several electronic and mechanical components can be positioned inside the spherical housing 202 for enabling processing, wireless communication, propulsion, and other functions. Among the components, a drive system 201 can be included to enable the device to propel itself. The drive system 201 can be coupled to processing resources and other control mechanisms as described above with reference to FIG. 1. Referring still to FIG. 2A, a carrier 214 can be included to serve as an attachment point and support for electronic components of the self-propelled device 200. The drive system 201, energy storage unit 216, carrier 214, biasing mechanism 215, other components such as described above with reference to FIG. 1, and any payload items that can ultimately occupy a payload space 228, cannot be rigidly mounted to the spherical housing 202. Instead, wheels 218, 220 included in the drive system 201 can be in frictional contact with the inner surface 204 of the spherical housing 202, and can function to drive the spherical housing 202 by the action of the actuators.

The carrier 214 can be in mechanical and electrical contact with the energy storage unit 216. The energy storage unit 216 can provide a reservoir of energy to power the device and electronics and can be replenished via the inductive charge port 226. For example, the energy storage unit 216 can a rechargeable battery and can be composed of lithium-polymer cells.

The carrier 214 can provide a mounting location for most of the internal components, including printed circuit boards for electronic assemblies, the sensor array, one or more antenna, and one or more connectors, as well as providing a mechanical attachment point for internal components. Further, the carrier 214 can provide a base for payloads being placed within the self-propelled device 200. In this manner, the top surface of the carrier 214 can also be the floor of the payload space 228. However, other configurations of the payload space 228 are contemplated, such as for example, a payload space 228 specially formed for a camera, or one that includes compartments for carrying multiple items.

The drive system 201 includes motors 222, 224 and the wheels 218, 220. The motors 222, 224 connect to the wheels 218, 220 independently through an associated shaft, axle, and gear drive (not shown). The wheels 218, 220 can be in physical contact with inner surface 204. The points where wheels 218, 220 contact the inner surface 204 are an essential part of the drive mechanism of the self-propelled device 200, and so are preferably coated with a material to increase friction and reduce slippage. For example, the circumference of the wheels 218, 220 can be coated with silicone rubber tires.

The biasing mechanism 215 can be included to actively force the wheels 218, 220 against the inner surface 204. As an example, a spring 212 and spring end 210 can comprise the biasing mechanism 215. More specifically, the spring 212 and the spring end 210 can be positioned to contact the inner surface 204 at a point diametrically opposed to the wheels 218, 220. The spring 212 and the spring end 210 can provide contact force to reduce or substantially eliminate slippage of the wheels 218, 220. The spring 212 is selected to provide a small force pushing wheels 218, 220, and the spring end 210 evenly against inner surface 204.

The spring end 210 provides near-frictionless contact with the inner surface 204. As such, the spring end 210 comprises a rounded or quasi-rounded surface configured to slide along the inner surface 204 as the self-propelled device 200 is driven by the drive system 201. Additional means of providing near-frictionless contact can be included. In some implementations, the spring end 210 can include one or more bearings to further reduce friction at the contact point where the spring end 210 moves along the inner surface 204. Furthermore, the spring 212 and the spring end 210 can be composed of a non-magnetic material to avoid interference with sensitive magnetic sensors.

The payload space 228 can be incorporated to carry a single payload or multiple payloads for civilian and/or military activities. The payload space 228 can be arranged to carry any number of payloads, including, for example, one or more of: a camera for surveillance or remote video stream, an infrared sensor, a chemical or biological sensor to detect harmful agents, an explosive or flash bang that can be maneuvered into place and detonated, and/or a listening device.

FIG. 2B is an example block diagram illustrating a self-propelled device with an alternative biasing mechanism 217. Referring to FIG. 2B, the biasing mechanism 217 can incorporate a chassis 237 which can include one or more additional wheels 234, 236 to increase or reconfigure the payload space 228. The biasing mechanism 217 can include a center post 238 configured to exert a force against the chassis 237 which can, in turn, press the additional wheels 234, 236 against inner surface 204 of the spherical housing 202. The center post 238 may or may not include a spring 240 to aid in the biasing. Alternatively, the chassis 237 may be placed proximate to the drive system 201 such that the wheels 218, 220, 234, and 236 contact the inner surface 204 in the same hemisphere, as opposed to being diametrically opposite. As an addition or alternative, the chassis 237 may be positioned such that the center post 238 forms an angle, wherein the additional wheels 234, 236 contact the inner surface 204 slightly above the equator (in a reference frame where the drive system 201 is positioned at the very bottom of the self-propelled device 200). These arrangements, and similar arrangements, may be included to, for example, maximize or optimize the payload space 228.

FIG. 2C is an example block diagram illustrating a self-propelled device with another alternative biasing mechanism to improve payload space 250. For example, an independent biasing mechanism 252 can be included configured to actively force the drive system wheels 218, 220 against the inner surface 204, similar to the biasing mechanisms discussed above with respect to FIGS. 2A and 2B. The independent biasing mechanism 252 is comprised of two or more separate portal axles 258, 260. The portal axles 258, 260 may include springs to press respective wheels 254, 256 against the inner surface 204 with a force vector having a vertical value. The vertical force from the wheels 254, 256 pressing against the inner surface 204 in turn, actively forces the drive system 201 and its respective wheels 254, 256 against the inner surface 204 as well, thereby providing sufficient force for the drive system 201 to cause the self-propelled device 200 to move.

As shown, the independent biasing mechanism 252 with its two or more portal axles 258, 260 allows for significantly increased payload space 250, whereby any number of different types or sizes of payload (e.g. a camera, infrared sensor, chemical or biological sensor, one or more explosives, a listening device, etc.) can be positioned within the space 250. By removing the biasing mechanism configurations as shown by examples of FIGS. 2A and 2B, and replacing them with an independent biasing mechanism 252 with independent portal axles 258, 260, the interior of the self-propelled device 200 can be cleared to provide a spacious interior. The portal axles 258, 260 comprising the independent biasing mechanism 252 can be mounted directly onto the carrier 214. The springs corresponding to the portal axles 258, 260 may be in the form of torsion springs which force the wheels 254, 256 against the inner surface 204. As an addition or alternative, the springs may be comprised of one or more of a compression spring, clock spring, or tension spring. Alternatively, the portal axles 258, 260 can be mounted in such a manner in which no springs are included to maintain a force pressing the drive system 201 and wheels 218, 220 against the inner surface 204, allowing sufficient traction to cause the self-propelled device 200 to move.

FIG. 3 is an example block diagram illustrating a self-propelled device including a camera. The multi-purpose self-propelled device 300 can include a camera 302 mounted within the payload space 310. For example, the spherical housing 304 is transparent to allow the camera 302 to view outside the self-propelled device 300. The camera 302 can be mounted on the biasing mechanism, or otherwise mounted within the self-propelled device 300 in order to maintain a substantially level orientation. For example, the camera 302 can be mounted to the carrier 314 to achieve the same.

The camera 302 can be mounted on a gyroscope or other stabilizing means so that the camera's orientation can be more substantially level with an outside reference frame. For example, the stabilizing means (not shown) can be mounted on the biasing mechanism 315 and/or the carrier 314 in order to achieve further stability and to further maintain orientation. For self-propelled devices 300 having an independent biasing mechanism using portal axles as discussed with respect to FIG. 2C, the camera 302 can be mounted to the carrier 314.

As an addition or alternative, the camera 302 can further be coupled to the wireless communication module. The camera 302 can provide photographs and/or a video stream to the controller device 306 by way of a wireless link 308. In similar arrangements, the self-propelled device can be remotely controlled by a user using the controller device 306 via the wireless link 308. As implemented, the self-propelled device 300 can be controlled utilizing the video stream, and therefore, the user need not be in visual sight of the self-propelled device 300 in order to maintain effective operation.

The camera 302 can be any photo or video recording device. The camera 302 can itself contain wireless communication means, such that it may directly link with the controller device 306. Alternatively, the camera 302 can be coupled to the processor and the video stream may be fed to the controller device 306 via the wireless module included in the system as described above with respect to FIG. 1.

The controller device 306 can be a remote control, smartphone, tablet, or a customized device capable of storing and executing applications or instructions to operate the self-propelled device 300. For example, the controller device 306 can be in the form of a smartphone or tablet, and operation of the self-propelled device can be executed by way of an application stored in the smartphone or tablet. Alternatively, the controller device 306 and self-propelled device 300 can be manufactured as a combined system specially manufactured for one or more purposes. For example, the combined system of the self-propelled device 300 and the controller device 306 can be used specifically for surveillance. Further, an application of the controller device 306 can include a “touch and drive” feature, wherein the user can touch the display of the controller device 306 corresponding to a selected location, and caused the self-propelled device 300 to maneuver to that location. The “touch and drive” feature can further allow the user to select a location on the display of the controller device 306, where the selected location corresponds to the same location on the video stream. In other words, the user can “touch” a location on the video stream from the self-propelled device 300, and the self-propelled device 300 will automatically maneuver itself to that location.

FIG. 4 is an example block diagram illustrating a self-propelled device including a payload. Referring to FIG. 4, the self-propelled device includes a payload space 406 to carry and transport specific items or payload 404 for various activities. Such items can include one or more of: an infrared sensor, a chemical or biological sensor, an explosive or flash bang, a listening device, other mechanical devices, and the like. Any one or more of these items can further be included in variations including a camera as described above with reference to FIG. 3.

As shown in an example of FIG. 4, the self-propelled device 400 includes a payload space 406 for carrying a payload 404. The self-propelled device 400 can be constructed in manner in which it can be thrown by a user, and then controlled via the controller device 412. A protective cover 402 can be included to dampen shock when, for example, the self-propelled device 400 is thrown by a user. The protective cover 402 can be removable and/or can be configured to break away from the self-propelled device 400 during periods of extreme shock. In such examples, the self-propelled device 400 can break free of the protective cover 402 and proceed with its intended purpose.

The protective cover 402 can be included to seal or waterproof the self-propelled device 400. For example, the self-propelled device 400 can be further configured to float or sink depending on its intended application. Furthermore, the self-propelled device 400 can float when deposited into water in order to be easily retrievable.

Examples as shown in FIG. 4 can be manufactured for a singular purpose, or can be configured to be loaded and unloaded multiple times. The latter can include a spherical housing 408 and/or a protective cover 402 that can be readily opened or closed by a user. Single purpose examples can be manufactured to be permanently sealed, and the payload 404 of such arrangements can be selected for the singular purpose. For example, the payload 404 can be an explosive, where the self-propelled device 400 is utilized for a single use. As implemented, the self-propelled device 400 can be maneuvered to a selected location and then detonated, effectively destroying the self-propelled device 400.

Alternatively, the self-propelled device 400 can be configured to open upon a command prompt by a user and deposit its payload 404 at a selected location. The user can then cause the spherical housing 408 to close using the controller device 412 and proceed to continue maneuvering the self-propelled device 400. Furthermore, the self-propelled device 400 and controller device 412 can include the “touch and drive” feature as described above with respect to FIG. 4.

FIG. 5 is an example schematic depiction of a self-propelled device 514 and a controller device 508. More specifically, the self-propelled device 514 can be controlled in its movement by programming logic and/or controls that can originate from the controller device 508. The self-propelled device 514 is capable of movement under control of the controller device 508, which can be operated by a user 502. The controller device 508 can wirelessly communicate control data to the self-propelled device 514 using a standard or proprietary wireless communication protocol. In variations, the self-propelled device 514 can be at least partially self-controlled, utilizing sensors and internal programming logic to control the parameters of its movement (e.g., velocity, direction, etc.). Still further, the self-propelled device 514 can communicate data relating to the device's position and/or movement parameters for the purpose of generating or alternating content on the controller device 508. In additional variations, self-propelled device 514 can control aspects of the controller device 508 by way of its movements and/or internal programming logic.

As described herein, the self-propelled device 514 can have multiple modes of operation, including those of operation in which the device is controlled by the controller device 508, is a controller for another device (e.g., another self-propelled device or the controller device 508), and/or is partially or wholly self-autonomous.

Additionally, the self-propelled device 514 and the controller device 508 can share a computing platform on which programming logic is shared, in order to enable, among other features, functionality that includes: (i) enabling the user 502 to operate the controller device 508 to generate multiple inputs, including simple directional input, command input, gesture input, motion or other sensory input, voice input or combinations thereof; (ii) enabling the self-propelled device 514 to interpret inputs received from the controller device 508 as a command or set of commands; and/or (iii) enabling the self-propelled device 514 to communicate data regarding that device's position, movement and/or state in order to effect a state on the controller device 508 (e.g., display state, such as content corresponding to a controller-user interface). Furthermore, the self-propelled device 514 can include a programmatic interface that facilitates additional programming logic and/or instructions to use the device. The controller device 508 can execute programming that is communicative with the programming logic on the self-propelled device 514.

Accordingly, the self-propelled device 514 can include an actuator or drive mechanism causing motion or directional movement. The self-propelled device 514 can be referred to by a number of related terms and phrases, including controlled device, robot, robotic device, remote device, autonomous device, and remote-controlled device. In variations, the self-propelled device 514 can be structured to move and be controlled in various media. For example, the self-propelled device 514 can be configured for movement in media such as on flat surfaces, sandy surfaces, or rocky surfaces.

The self-propelled device 514 can be implemented in various forms. For example, the self-propelled device 514 can correspond to a spherical object that can roll and/or perform other movements such as spinning. In variations, the self-propelled device 514 can correspond to a radio-controlled aircraft, such as an airplane, helicopter, hovercraft or balloon. In other variations, the self-propelled device 514 can correspond to a radio controlled watercraft, such as a boat or submarine. Numerous other variations can also be implemented, such as those in which the self-propelled device 514 is a robot.

Furthermore, the self-propelled device 514 can include a sealed hollow housing, roughly spherical in shape, capable of directional movement by action of actuators inside the enclosing envelope.

Referring still to FIG. 5, the self-propelled device 514 can be configured to communicate with the controller device 508 using network communication links 510 and 512. Link 510 can transfer data from the controller device 508 to the self-propelled device 514. Link 512 can transfer data from the self-propelled device 514 to the controller device 508. Links 510 and 512 are shown as separate unidirectional links for illustration. As an example, a single bi-directional communication link performs communication in both directions. Link 510 and link 512 are not necessarily identical in type, bandwidth or capability. For example, communication link 510 from controller device 508 to self-propelled device 514 is often capable of a higher communication rate and bandwidth compared to link 512. In some situations, only one link 510 or 512 is established. In such examples, communication is unidirectional.

The controller device 508 can correspond to any device comprising at least a processor and communication capability suitable for establishing at least unidirectional communications with the self-propelled device 514. Examples of such devices include, without limitation: mobile computing devices (e.g., multifunctional messaging/voice communication devices such as smart phones), tablet computers, portable communication devices and personal computers. For example, the controller device 508 is an IPHONE available from APPLE COMPUTER, INC. of Cupertino, Calif. In another example, the controller device 508 is an IPAD tablet computer, also from APPLE COMPUTER. In still other examples, the controller device 508 is any of the handheld computing and communication appliances executing the ANDROID operating system from GOOGLE, INC.

Elsewise, the controller device 508 can be a personal computer, in either a laptop or desktop configuration. For example, the controller device 508 can be a multi-purpose computing platform running the MICROSOFT WINDOWS operating system, or the LINUX operating system, or the APPLE OS/X operating system, configured with an appropriate application program to communicate with the self-propelled device 514.

In variations, the controller device 508 can be a specialized device dedicated for enabling the user 502 to control and interact with the self-propelled device 514.

Furthermore, multiple types of controller devices 508 can be used interchangeably to communicate with the self-propelled device 514. Additionally or as an alternative, the self-propelled device 514 can be capable of communicating and/or being controlled by multiple devices (e.g., concurrently or one at a time). For example, the self-propelled device 514 can be capable of being linked with an IPHONE in one session and with an ANDROID device in a later session, without modification of the device 514.

Accordingly, the user 502 can interact with the self-propelled device 514 via the controller device 508, in order to control the self-propelled device 514 and/or to receive feedback or interaction on the controller device 508 from the self-propelled device 514. Furthermore, the user 502 can specify a user input 504 through various mechanisms that are provided with the controller device 508. Examples of such inputs include text entry, voice command, touching a sensing surface or screen, physical manipulations, gestures, taps, shaking and combinations of the above.

The user 502 can interact with the controller device 508 in order to receive feedback 506. The feedback 506 can be generated on the controller device 508 in response to user input. As an alternative or addition, the feedback 506 can also be based on data communicated from the self-propelled device 514 to the controller device 508, regarding, for example, the self-propelled device's 514 position or state. Without limitation, examples of feedback 506 include text display, graphical display, sound, music, tonal patterns, modulation of color or intensity of light, haptic, vibrational or tactile stimulation. The feedback 506 can be combined with input that is generated on the controller device 508. For example, the controller device 508 can output content that can be modified to reflect position or state information communicated from the self-propelled device 514.

As an example, the controller device 508 and/or the self-propelled device 514 can be configured such that user input 504 and feedback 506 maximize usability and accessibility for the user 502, who has limited sensing, thinking, perception, motor or other abilities. This allows users with handicaps or special needs to operate the system 500 as described.

A configuration as illustrated in FIG. 5, can be only one of an almost unlimited number of possible configurations of networks including a self-propelled device 514 with communication connections. Furthermore, while numerous variations described herein provide for a user to operate or otherwise directly interface with the controller device 508 in order to control and/or interact with a self-propelled device, variations described encompass enabling the user to directly control or interact with the self-propelled device 514 without use of an intermediary device such as the controller device 508.

FIG. 6 illustrates an example technique for causing motion of a self-propelled spherical device 600. As shown by an example of FIG. 6, the device 600 has a center of rotation 602 and a center of mass 606, the device 600 being contact with planar surface 612. The drive mechanism for the robotic device 600 comprises two independently-controlled wheeled actuators 608 in contact with the inner surface of the enclosing spherical envelope of device 600. Also shown is sensor platform 604. Several components of device 600 are not shown in FIG. 6 for simplicity of illustration.

To achieve continuous motion at a constant velocity, the displacement of center of mass 606 relative to center of rotation 602 can be maintained by action of wheeled actuators 608. The displacement of the center of mass 606 relative to the center of rotation 602 is difficult to measure, thus it is difficult to obtain feedback for a closed-loop controller to maintain constant velocity. However, the displacement is proportional to the angle 610 between sensor platform 604 and surface 612. The angle 610 can be sensed or estimated from a variety of sensor inputs, as described herein. Therefore, the speed controller for robotic device 600 can be implemented to use angle 610 to regulate speed for wheeled actuators 608 causing the device 600 to move at a constant speed across the surface 612. The speed controller can determine the desired angle 610 to produce the desired speed, and the desired angle set point can be provided as an input to a closed loop controller regulating the drive mechanism.

FIG. 6 illustrates use of angle measurement for speed control. However, the technique can further be extended to provide control of turns and rotations, with feedback of appropriate sensed angles and angular rates.

It can be seen from the foregoing discussion that knowledge of the orientation angles is useful, in variations, for control of the self-propelled device 600. Measuring the orientation of the device can also be useful for navigation and alignment with other devices.

FIG. 7 is an example block diagram depicting a sensor array and data flow. Referring to FIG. 7, the sensor array 712 can include a set of sensors for providing information to the self-propelled device, including for example, its position, orientation, rates of translation, rotation, and acceleration. Many other sensors can be included to meet requirements in various examples.

In variations, the sensor array 712 can include a three-axis gyroscopic sensor 702, a three-axis accelerometer sensor 704, and a three-axis magnetometer sensor 706. In certain variations, a receiver for a Global Positioning System (GPS) is included 710. However, GPS signals are typically unavailable indoors, so the GPS receiver can be omitted.

Due to limitations in size and cost, the sensors in sensor array 712 can be miniaturized devices employing micro-electro-mechanical (MEMS) technology. The data from these sensors can require filtering and processing to produce accurate state estimates 716. Various algorithms can be employed in sensor fusion and state estimator 714. These algorithms can be executed by the processor on the self-propelled device.

Those familiar with the art will understand that the signals from sensor in sensor array 712 can be imperfect and distorted by noise, interference, and the limited capability of inexpensive sensors. However, the sensors can also provide redundant information, so that application of a suitable sensor fusion and state estimator process 714 can provide an adequate state estimation 716 of the true state of the self-propelled device.

For example, in many situations, magnetometer data is distorted by stray magnetic fields and ferrous metals in the vicinity. Sensor fusion and state estimator 714 can be configured to reject bad or suspect magnetometer data and rely on the remaining sensors in estimating the state 716 of the self-propelled device. In some examples, particular movements of the self-propelled device can be used to improve sensor data for desired purposes. For example, it can be useful to rotate self-propelled device through an entire 360 degree heading sweep while monitoring magnetometer data, to map local magnetic fields. Since the fields are usually relatively invariant over a short period of time, the local field measurement is repeatable and therefore useful, even if distorted.

Architecture

FIG. 8 illustrates an example system including a self-propelled device 810 and a controller device 850 that controls and interacts with the self-propelled device 810. The self-propelled device 810 can be constructed using hardware resources such as described by examples of FIG. 1. Accordingly, the self-propelled device 810 can be a spherical object such as described by examples with respect to FIGS. 2-4. The controller device 850 can be a multifunctional device, such as a mobile computing device (e.g., smart phone), tablet, or personal computer. Alternatively, the controller device 850 can correspond to a specialized device that is dedicated to controlling and communicating with the self-propelled device 810.

The self-propelled device 810 can execute one or more programs 816 stored in a program library 820. Each program 816 in the program library 820 can include instructions or rules for operating the device, including instructions for how the device is to respond to specific conditions, how the device is to respond to a control input 813 (e.g., user input entered on the controller device 850), and/or the mode of operation that the device is to implement (e.g., controlled mode, versus autonomous, etc.).

The program library 820 can also maintain an instruction set that can be shared by multiple programs, including instructions that enable some user inputs to be interpreted in a common manner. An application program interface (API) 830 can be implemented on the device 810 to enable programs to access a library of functions and resources of the device. For example, the API 830 can include functions that can be used with programs to implement motor control (e.g., speed or direction), state transition, sensor device interpretation, and/or wireless communications.

In certain implementations, the device 810 can receive programs and programming instructions wirelessly through the use of a wireless communication port 812. In variations, the device 810 can receive programs and programming instructions 882 from external sources 880 via other ports, such as an expansion port 120 (see FIG. 1). The programming resources can originate from, for example, a media provided to the user of the device (e.g., SD card), a network resource or website where programs can be downloaded, and/or programs and/or instruction sets communicated via the wireless communication port 812 from the controller device 850. In several implementations, the controller device 850 can be programmatically configured to interact and/or control the self-propelled device 810 with software. Once configured, the controller device 850 can communicate instructions coinciding with its programmatic configuration to the self-propelled device 810. For example, the controller device 850 can download an application for controlling or interacting with the self-propelled device 810. The application can be downloaded from, for example, a network (e.g., from an App Store), or from a website, using wireless communication capabilities inherent in the controller device 850 (e.g., cellular capabilities, Wi-Fi capabilities, etc.). The application that is downloaded by the controller device 850 can include an instruction set that can be communicated to the self-propelled device 810.

The controller device 850 can execute a program 856 that is specialized or otherwise specific to communicating or interacting with, and/or controlling the self-propelled device 810. In variations, the program 856 that executes on the controller device 850 can include a counterpart program 816A that can execute on the self-propelled device 810. The programs 856, 816A can execute as a shared platform or system. For example, as described below, the program 856 operating on the controller device 850 can cooperate with the counterpart runtime program 816A to generate input for the self-propelled device 810, and to generate output on the controller device 850 based on a data signal from the self-propelled device 810. For example, the program 856 can generate a user interface 860 that (i) prompts or provides guidance for the user to provide input that is interpretable on the self-propelled device 810 as a result of the counterpart runtime program 816A, resulting in some expected outcome from the self-propelled device 810; and (ii) receives feedback 818 from the self-propelled device 810 in a manner that affects the content that is output by the program 856 operating on the controller device 850. In the latter case, for example, computer-generated content can be altered based on positioning or movement of the self-propelled device 810.

More specifically, on the controller device 850, the program 856 can provide a user interface 860, including logic 862 for prompting and/or interpreting user input on the controller device. Various forms of input can be entered on the controller device 850, including, for example, user interaction with mechanical switches or buttons, touchscreen input, audio input, gesture input, or movements of the device in a particular manner.

Accordingly, the program 856 can be configured to utilize an inherent application program interface on the controller device 850, to utilize the various resources of the device to receive and process input. Many existing multifunctional or general purpose computing devices (e.g., smart phones or tablets) can be configured to detect various kinds of input, including touchscreen input (e.g., multi-touch input or gesture input), optical input (e.g., camera image sensing input), audio input and device movement input (e.g., shaking or moving the entire device). The user interface 860 can include logic 862 to prompt the user for specific kinds of input (e.g., include visual markers where a user should place fingers, instruct the user or provide the user with the visual and/or audio prompt to move the device, etc.), and to interpret the input into control information that is signaled to the self-propelled device 810.

In some implementations, the input generated on the controller device 850 can be interpreted as a command and then signaled to the self-propelled device 810. In other implementations, the input entered on the controller device 850 can be interpreted as a command by programmatic resources on the self-propelled device 810. By interpreting user input in the form of commands, the self-propelled device 810 can respond to user input in a manner that is intelligent and configurable. For example, the self-propelled device 810 can interpret user input that is otherwise directional in nature in a manner that is not directional. For example, a user can enter gesture input corresponding to a direction, in order to have the self-propelled device 810 move in a manner that is different than the inherent direction in the user input. For example, a user can enter a leftward gesture, which the device can interpret (based on the runtime program 816A) as a command to stop, spin, return home, or alter illumination output, etc.

The user interface 860 can also include output logic 864 for interpreting data received from the self-propelled device 810. As such, the self-propelled device 810 can communicate information, such as state information and/or position information (e.g., such as after when the device moves) to the controller device 850. In one implementation, the communication from the self-propelled device 810 to the controller device 850 can be in response to a command interpreted from user input on the controller device 850. In another implementation, the communication from the self-propelled device 810 can be in the form of continuous feedback generated as result of the device's continuous movement over a duration of time. In variations, the output onto device 850 can correspond to a controller device having one of various possible form factors. The program 856 can configure the interface to graphically provide gaming context and/or different user-interface paradigms for controlling the self-propelled device 810. The program 856 can operate to directly affect the content generated in these implementations based on movement, position, or state of the self-propelled device 810.

In operation, the self-propelled device 810 can implement the programmatic runtime 816A using one or more sets of program instructions stored in its program library 820. The program runtime 816A can correspond to, for example, a program selected by the user, or one that is run by default or in response to some other condition or trigger. Among other functionality, the program runtime 816A can execute a set of program-specific instructions that utilizes device functions and/or resources in order to: (i) interpret control input from the controller device 850; (ii) control and/or state device movement based on the interpretation of the input; and/or (iii) communicate information from the self-propelled device 810 to the controller device 850.

The program runtime 816A can implement drive control logic 831, including sensor control logic 821 and input control logic 823. The sensor control logic 821 can interpret device sensor input 811 for controlling speed, direction, or other movement of the self-propelled device's drive system or assembly. The sensor input 811 can correspond to data such as provided from the accelerometer(s), magnetometer(s), and/or gyroscope(s) of the self-propelled device 810. The sensor data can also include other information obtained on a device regarding the device's movement, position, state or operating conditions, including GPS data, temperature data, etc. The program 816A can implement parameters, rules or instructions for interpreting sensor input 811 as drive assembly control parameters 825. The input control logic 823 can interpret control input 813 received from the controller device 850. In some implementations, the logic 823 can interpret the input as a command, in outputting drive assembly control parameters 825 that are determined from the input 813. The input drive logic 823 can also be program specific, so that the control input 813 and/or its interpretation are specific to the runtime program 816A. The drive assembly control logic can use the parameters, as generated through sensor/input control logic 821, 823 to implement drive assembly controls.

In variations, the sensor/input control logic 821, 823 can be used to control other aspects of the self-propelled device 810. In variations, the sensor/input control logic 821, 823 can execute runtime program 816A instructions to generate a state output 827 that can control a state of the device in response to some condition, such as user input or device operation condition (e.g., the device comes to stop). For example, an illumination output (e.g., LED display out), audio output, or device operational status (e.g., mode of operation and/or power state) can be affected by the state output 827.

Additionally, the run time program 816A can generate an output interface 826 for the self-propelled device program 856 running on the controller device 850. The output interface 826 can generate the data that comprises feedback 818. For example, the output interface 826 can generate data that is based on position, movement (e.g., velocity, rotation), state (e.g., state of output devices), and/or orientation information (e.g., position and orientation of the device relative to the initial reference frame). The output interface 826 can also generate data that, for example, identifies events that are relevant to the runtime program 816A. For example, the output interface 826 can identify events such as the device being disrupted in its motion or otherwise encountering a disruptive event. The output interface 826 can also generate program specific output, based on, for example, instructions of the runtime program 816A. For example, the run-time program 816A can require a sensor reading that another program would not require. The output interface 826 can implement instructions for obtaining the sensor reading in connection with other operations performed through implementation of the runtime program 816A.

Furthermore, the self-propelled device 810 can be operable in multiple modes relative to the controller device 850. In a controlled mode, the self-propelled device 810 can be controlled in its movement and/or state by control input 813 via control signals communicated from the controller device 850. In some implementations, the self-propelled device 810 can pair with the controller device 850 in a manner that affects operations on the controller device 850 as to control or feedback. The self-propelled device 810 can also be operable in an autonomous mode, where control parameters 825 are generated programmatically on the device in response to, for example, sensor input 811 and without need for control input 813. Further, the self-propelled device 810 can be operated along with the controller device 850 in a “touch and drive” mode, wherein the user can touch a selected location on a video stream of the self-propelled device 810, and the self-propelled device 810 can autonomously maneuver to the corresponding location. Still further, in variations, the self-propelled device 810 can act as a controller, either for the controller device 850 or for another self-propelled device 810. For example, the device can move to affect a state of the controller device 850. The device can operate in multiple modes during one operating session. The mode of operation can be determined by the runtime program 816A.

The self-propelled device 810 can include a library of instruction sets for interpreting control input 813 from the controller device 850. For example, the self-propelled device can store instructions for multiple programs, and the instructions for at least some of the programs can include counterpart programs that execute on the controller device 850. The library maintained on the self-propelled device can be dynamic, in that the instructions stored can be added, deleted or modified. For example, a program stored on the self-propelled device can be added, or another program can be modified.

When executed on the controller device 850, each program includes instructions to recognize a particular set of inputs, and different programs can recognize different inputs. For example, a golf program can recognize a swing motion on the controller device 850 as an input, while the same motion can be ignored by another program that is dedicated to providing a virtual steering mechanism. When executed on the self-propelled device 810, each program can include instructions to interpret or map the control input 813 associated with a particular recognized input to a command and control parameter.

In variations, the self-propelled device can be able to dynamically reconfigure its program library. For example a program can be modified (e.g., through instructions received by the controller device 810) to process control input 813 that corresponds to a new recognized input. As another example, the self-propelled device 810 can be able to switch programs while the self-propelled device 810 is in use. When programs are switched, a different set of inputs can be recognized, and/or each input can be interpreted differently on the self-propelled device 810.

Touch and Drive Method

FIG. 9 is a flow chart illustrating an example method of operating a self-propelled device. Referring to FIG. 9, a user of a controller device (e.g., a smart phone, table, remote control, or other mobile computing device) can receive an image or a video feed from a self-propelled device. The self-propelled device need not be spherical in nature, but rather can be any device capable of being controlled by a controller device as described herein. The self-propelled device can be configured to include, among other features, a transparent spherical housing, a camera positioned within the housing, and a wireless link which can stream the video feed to the controller device. In this manner, the controller device can receive the feed from the camera positioned within the self-propelled device (900). Further, the controller device can include a display screen, such that the feed can be displayed on the controller device (902). The controller device can include touch screen features that allow the user to interact directly with the displayed feed.

The user can then select an object or location point on the displayed video feed. Accordingly, the user selection of the location point is received by the controller device (904). The user can select the location point by touching an object on the screen corresponding to the physical object in the self-propelled device's frame of reference. Additionally or alternatively, the user can provide voice commands that identify the object being displayed. Upon receiving the selection by the user, the controller device can then generate a command signal based on position information to the self-propelled device, causing it to traverse to the physical location point (908). The self-propelled device can traverse directly to the object, or perform maneuvers around obstacles to ultimately arrive at the object's location.

As an addition or alternative, the controller device can be further configured to determine a position of the object depicted on the display screen based on the user's and/or controller device's reference frame. The controller device can also map the relative position of the location point displayed on the controller device with a position of the location point in the self-propelled device's reference frame (906). In this manner, the self-propelled device can be directed by the controller device to traverse to the location of the object based on the mapped relative positions via the image/video feed, wherein the controller device can include processing means to calculate the relative positions.

CONCLUSION

One or more examples described herein provide that methods, techniques and actions performed by a computing device are performed programmatically, or as a computer-implemented method. Programmatically means through the use of code, or computer-executable instructions. A programmatically performed step may or may not be automatic.

One or more examples described herein can be implemented using programmatic modules or components. A programmatic module or component may include a program, a subroutine, a portion of a program, or a software component or a hardware component capable of performing one or more stated tasks or functions. As used herein, a module or component can exist on a hardware component independently of other modules or components. Alternatively, a module or component can be a shared element or process of other modules, programs or machines.

Furthermore, one or more examples described herein may be implemented through the use of instructions that are executable by one or more processors. These instructions may be carried on a computer-readable medium. Machines shown or described with FIGs below provide examples of processing resources and computer-readable mediums on which instructions for implementing examples of the invention can be carried and/or executed. In particular, the numerous machines shown with examples of the invention include processor(s) and various forms of memory for holding data and instructions. Examples of computer-readable mediums include permanent memory storage devices, such as hard drives on personal computers or servers. Other examples of computer storage mediums include portable storage units (such as CD or DVD units), flash memory (such as carried on many cell phones and tablets)), and magnetic memory. Computers, terminals, network enabled devices (e.g., mobile devices such as cell phones) are all examples of machines and devices that utilize processors, memory and instructions stored on computer-readable mediums. Additionally, examples may be implemented in the form of computer-programs, or a computer usable carrier medium capable of carrying such a program.

Although illustrative examples have been described in detail herein with reference to the accompanying drawings, variations to specific examples and details are encompassed by this disclosure. It is intended that the scope of the invention is defined by the following claims and their equivalents. Furthermore, it is contemplated that a particular feature described, either individually or as part of an example, can be combined with other individually described features, or parts of other examples. Thus, absence of describing combinations should not preclude the inventor(s) from claiming rights to such combinations.

While certain examples of the inventions have been described above, it will be understood that the examples described are by way of example only. Accordingly, the inventions should not be limited based on the described examples. Rather, the scope of the inventions described herein should only be limited in light of the claims that follow when taken in conjunction with the above description and accompanying drawings. 

What is claimed is:
 1. A self-propelled device comprising: a spherical housing; a drive system disposed within the spherical housing, the drive system to power one or more wheels; a carrier mounted atop the drive system, the carrier having a top surface corresponding to a floor of a payload space within the spherical housing; and a biasing mechanism coupled to the carrier, the biasing mechanism to actively force the one or more wheels to continuously engage an inner surface of the spherical housing in order to cause the spherical housing to move.
 2. The self-propelled device of claim 1, further comprising a protective cover encasing the spherical housing, the protective cover configured to break away during periods of intense shock.
 3. The self-propelled device of claim 1, further comprising: one or more batteries coupled to the drive system; and an inductive charge port coupled to the one or more batteries, the inductive charge port to enable inductive charging of the one or more batteries.
 4. The self-propelled device of claim 1, further comprising a charging port coupled to one or more batteries disposed within the self-propelled device and coupled to the drive system, the charging port configured for plug-in charging of the one or more batteries.
 5. The self-propelled device of claim 1, wherein the biasing mechanism comprises a left portal axle and a right portal axle, each of the left portal axle and the right portal axle mounted to the carrier and including a spring coupled to a contact surface to provide a force against the inner surface of the spherical housing, wherein the force includes a vertical vector providing sufficient biasing to actively force the one or more wheels to continuously engage the inner surface of the spherical housing in order to cause the spherical housing to move.
 6. The self-propelled device of claim 5, further comprising a camera coupled to the floor of the payload space between the left portal axle and the right portal axle, wherein the spherical housing is optically transparent.
 7. The self-propelled device of claim 6, further comprising a camera stabilizer mounted to the floor of the payload space between the left portal axle and the right portal axle, wherein the camera is mounted to the camera stabilizer.
 8. The self-propelled device of claim 1, further comprising one or more of: a chemical sensor, an infrared sensor, a motion sensor, a listening device, or a biological sensor disposed within the payload space.
 9. The self-propelled device of claim 1, further comprising one or more explosives disposed within the payload space.
 10. The self-propelled device of claim 1, wherein the spherical housing is sealable to permit the self-propelled device to be substantially waterproof.
 11. The self-propelled device of claim 1, further comprising a receiver coupled with a processor operating the drive system, the receiver to receive an instruction signal from an external controller and transmit the instruction signal to the processor, the processor to execute the instruction signal as a command to the drive system to maneuver the self-propelled device.
 12. The self-propelled device of claim 11, wherein the processor operates a door mechanism on the spherical housing, and wherein the spherical housing mechanically opens via the door mechanism upon opening instructions received by the processor from the external controller.
 13. The self-propelled device of claim 1, further comprising a stabilizer mounted to the floor of the payload space, the stabilizer including a gyroscope to maintain a substantially constant orientation for a payload when the self-propelled device is in motion.
 14. The self-propelled device of claim 13, wherein the stabilizer further includes a dampening system to reduce impact force on the payload during impacts on the self-propelled device.
 15. A computer-implemented method for operating a self-propelled device, the method performed by one or more processors of a mobile computing device and comprising: receiving an image from the self-propelled device, the image providing a field of view of an image capturing device mounted within the self-propelled device; displaying the image on a touch-sensitive display of the mobile computing device; receiving, on the touch-sensitive display, a user selection of a location point within the field of view of the image capturing device; and based on the user selection, generating a command signal to be transmitted to the self-propelled device, the command signal instructing the self-propelled device to maneuver to the location point.
 16. The method of claim 15, further comprising: determining a position of the location point in the field of view based on a first reference frame of the field of view as displayed on the mobile computing device; and mapping the position of the location point on a second reference frame corresponding to the location point relative to the self-propelled device; wherein the command signal is generated to include instructions for maneuvering the self-propelled device based solely on the second reference frame.
 17. The method of claim 15, wherein the image is a live video feed provided from the image capturing device within the self-propelled device, and wherein generating the command signal is performed dynamically in conjunction with receiving the live video feed.
 18. A non-transitory computer-readable medium storing instructions that, when executed by one or more processors of a mobile computing device, cause the mobile computing device to: receive an image from a self-propelled device, the image providing a field of view of an image capturing device mounted within the self-propelled device; display the image on a touch-sensitive display of the mobile computing device; receive, on the touch-sensitive display, a user selection of a location point within the field of view of the image capturing device; and based on the user selection, generate a command signal to be transmitted to the self-propelled device, the command signal instructing the self-propelled device to maneuver to the location point.
 19. The non-transitory computer-readable medium of claim 18, wherein the instructions, when executed by the one or more processors, further cause the mobile computing device to: determine a position of the location point in the field of view based on a first reference frame of the field of view as displayed on the mobile computing device; and map the position of the location point on a second reference frame corresponding to the location point relative to the self-propelled device; wherein the command signal is generated to include instructions for maneuvering the self-propelled device based solely on the second reference frame.
 20. The non-transitory computer-readable medium of claim 18, wherein the image is a live video feed provided from the image capturing device within the self-propelled device, and wherein generating the command signal is performed dynamically in conjunction with receiving the live video feed. 